Add initial LLM model support - #2629
Conversation
This creates a way to have a default llm provider so plugins can make simple inference. This was assisted by Claude Opus 4.7 Signed-off-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
|
I want to use this to have a one place to query for events for trace compass. It could be in the wrong place, but I strongly doubt anyone can have a wider need for AI than this, |
Test Results 57 files + 6 57 suites +6 36m 25s ⏱️ -41s For more details on these errors, see this check. Results for commit 76f1859. ± Comparison against base commit 9e8a07f. |
|
@MatthewKhouzam I don't understand what your target is here. I recently developed an MCP server for Eclipse so that LLMs can request informations from the Eclipse IDE. For example, my MCP server provides the problems in the workspace, can trigger builds and check references in Eclipse using the JDT AST. Can you explain your use case here? Your PR and commit message are unfortunately to short to understand what you mean. |
|
Hi, not an issue, I was just added support for eclipse to natively query llms via the OpenAI API, this is so that plug-ins don't need to re-implement the wheel everytime. It was a patch I made at OCX to get a discussion/ball rolling. The way I see it, eclipse would be the place you configure which model you want to use, then the plug-ins would just connect directly to the shared infrastructure. I made this to help out the Eclipse IDE Bof, it is not something I needed personally. Your MCP is the opposite, this was so Eclipse can call MCPs without using a third party... eventually. |
|
I re-open so that you could continue if you want |
This creates a way to have a default llm provider so plugins can make simple inference.
The intent is to have a way for all llms to work in a extensions that need inference. E.g. "explain this anomaly"
This was assisted by Claude Opus 4.7